Create scripts to validade if an app is still vulnerable to the attack narrative #447
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…could be exploited
Krlier
approved these changes
Oct 22, 2020
There was a problem hiding this comment.
Nice job, @alexandreBN! Thanks so much for this contribution! 🚀
If you, or anyone else, would like to work on creating more validation scripts, I'll reopen the issue with more details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This solution refers to which of the apps?
A/1# - SSType
A/4# - ViniJR Blog
Did you test your changes? What commands did you run?
Yes, in each application was inserted files to test if application is vulnerable to the attack narrative.
cd secDevLabs/owasp-top10-2017-apps/a1/sstype
make check-sec
cd secDevLabs/owasp-top10-2017-apps/a4/vinijr-blog
make check-sec